Client device with event wizard application and methods for use therewith

ABSTRACT

A client device includes at least one processor that executes an event wizard client application in conjunction with a user interface to display event type menu data, receive event type selection data, receive event size selection data, displaying event budget menu data, receive event budget selection data, display event budget data, displaying event option menu data, receive event option selection data, display event invitee menu data, and receive event invitee selection data.

CROSS REFERENCE TO RELATED PATENTS

The present application claims priority under 35 U.S.C. 119 to the provisionally filed application entitled, EVENT WIZARD SERVER AND METHODS FOR USE THEREWITH, having application Ser. No. 61/727,221, filed on Nov. 16, 2012; the contents of which are incorporated herein by reference thereto.

TECHNICAL FIELD OF THE INVENTION

The present invention relates to knowledge based systems used in conjunction with client/server network architectures.

DESCRIPTION OF RELATED ART

Planning a large social event such as a wedding can be an arduous process. There are many details that must be taken care of. This has led to the creation of specialized wedding planner services that involve professional wedding planner personnel that lead a bridge and groom through the required planning and decision making including the selection of vendors, materials and services. Though not as common, professional party planners can provide similar services for other events, particularly large events and functions that justify the cost of these services.

Evite is a social planning website that allows a user to create, send and manage online invitations to an event. A user creates online invitations (“Evites”) by entering e-mail addresses of prospective guests. The website automatically sends e-mails to the guests that contain the Evites. Each guest can respond by selecting a response such as: “Attending”, “Not Attending”, “Maybe”, and “Not yet replied”. Guests can also write additional comments, such as info for other guests, regrets, etc.

The limitations and disadvantages of conventional and traditional approaches will become apparent to one of ordinary skill in the art through comparison of such systems with the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 presents a pictorial representation of an event wizard server 25 and example devices 13-14 that operate in accordance with embodiments of the present invention.

FIG. 2 presents a block diagram representation of an event wizard server 25 in accordance with an embodiment of the present invention.

FIG. 3 presents a block diagram representation of a client device 100 in accordance with an embodiment of the present invention.

FIG. 4 presents a graphical representation of screen display 300 in accordance with an embodiment of the present invention.

FIG. 5 presents a graphical representation of screen display 310 in accordance with an embodiment of the present invention.

FIG. 6 presents a graphical representation of screen display 330 in accordance with an embodiment of the present invention.

FIG. 7 presents a graphical representation of screen display 340 in accordance with an embodiment of the present invention.

FIG. 8 presents a graphical representation of screen display 350 in accordance with an embodiment of the present invention.

FIG. 9 presents a graphical representation of screen display 360 in accordance with an embodiment of the present invention.

FIG. 10 presents a graphical representation of screen display 370 in accordance with an embodiment of the present invention.

FIG. 11 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

FIG. 12 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

FIG. 13 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

FIG. 14 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION INCLUDING THE PRESENTLY PREFERRED EMBODIMENTS

FIG. 1 presents a pictorial representation of an event wizard server 25 and example devices 13-14 that operate in accordance with embodiments of the present invention. In particular, an event wizard server 25 is presented that communicates with client devices such as mobile terminal 13 and personal computer 14 via network 15. The network 15 can be the Internet or other wide area communication network. The event wizard server 25 presents a website that operates via a browser application of mobile terminal 13 and/or personal computer 14 or that otherwise operates in conjunction with an application such as a mobile application to present a knowledge-based wizard process that leads a user through multiple prompts and steps to plan, implement and/or manage a social event such as: a Birthday Party, Anniversary, Dinner Party, Cocktail Party, Wedding and Reception, Baby Shower, Wedding Shower, Social Gathering, Fundraising event, Graduation Party, Bachelor Party, Bachelorette Party, Housewarming Party, Holiday Party (Christmas, New Years, Super Bowl, Valentines, Mardi Gras, Independence Day, etc. . . . ), Pot Luck Party.

In an embodiment, the event planning process begins with a user registering with the event wizard server 25, such as via an email address, and password. Event data in the form of prompts is presented to the client device for display relating to various options to be selected by the user for the event to be planned. Based on the type of event, the prompts direct the user towards a fully completed party or event. For example, the options can include a budget selected by the user, optionally with guidance from the wizard based on the type of event and other options. The event wizard server 25 can optionally issue notifications when user is within certain amount of reaching budget limit, present the budget impact of particular options and adjust the budget based on selection.

In an embodiment, the event wizard server 25 communicates with one or more content servers 12. These content servers 12 can be an invitation server such as Evite; a social networking server such as Facebook, MySpace, Twitter; an advertising server; and other servers that provide information on various event planning options including vendors, event supplies, equipment and other services pertaining to the food, drinks, entertainment, decorations, venues, etc. Information relating to an event to be planned can be stored in a database associated with the server or retrieved by the event wizard server 25 from the content server or servers 12 via network 15 and presented to the client device 13 or 14 as event data for selection by the user.

Event wizard server 25 and client devices 13 and 14 will be described in greater detail in conjunction with FIGS. 2-14, including several optional functions and features.

FIG. 2 presents a block diagram representation of an event wizard server 25 in accordance with an embodiment of the present invention. In particular, event wizard server 25 includes a network interface such as a network card or modem for communicating with client devices such as client devices 13 or 14, other servers such as content servers 12 via network 15. The event wizard server 25 also includes a processing module 230 and memory module 240 that stores an operating system 244 such as a Linux or Microsoft operating system or other operating system as well as an event wizard server application 250.

The processing module 230 can be implemented via a single processing device or a plurality of processing devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory, such as memory 240. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. While a particular bus architecture is presented that includes a single bus 260, other architectures are possible including additional data buses and/or direct connectivity between one or more elements. Further, the event wizard server 25 can include one or more additional elements that are not specifically shown.

In operation, at least one processor of the processing module 230 executes the event wizard server application 250 to bidirectionally communicate event planning data with a user of a client device, such as client device 13 or 14 via the network interface 220 and the network 15. In an embodiment, the event wizard server application 250 includes hardware, software or firmware such as an expert system, search engine, agent program, web crawler and/or database to identify and retrieve various event options for presentation to users. In particular, the event wizard server application 250 operates to filter options for presentation to the user based on one or more factors such as event budget, event size and location so that the user is presented with options that are most germane to the planned event. The event planning data includes information such as:

-   -   Event type menu data generated by the event wizard server         application 250 and sent to the client device that includes a         plurality of general event types and a plurality of specific         events;     -   Event type selection data received from the client device that         indicates an event type based on the event type menu data;     -   Event size selection data received from the client device that         indicates an event size;     -   Location data received from the client device;     -   Event budget menu data generated by event wizard server         application 250 and sent to the client device that includes a         plurality of budget options that are based on the event         selection data, the event size selection data and the location         data;     -   Event budget selection data received from the client device that         indicates a selected one of the plurality of budget options;     -   Event budget data generated by the event wizard server         application 250 in response to the selected one of the plurality         of plurality of budget options and sent to the client device;     -   Event option menu data that includes a plurality of event         options that are generated by the event wizard server         application 250 based on the event selection data and the         location data, wherein the event options correspond to at least         one of: an event venue, an event caterer, an event invitation,         event entertainment and event transportation, wherein the event         option menu data are sent to the client device;     -   Event option selection data received from the client device that         selects at least one event option based on the event option menu         data;     -   Event invitee menu data generated by the event wizard server         application 250 and sent to the client device that includes         contact data corresponding to the user that is retrieved by the         event wizard server from an external location via the network         interface; and     -   Event invitee selection data received from the client device         that indicates a plurality of invitees based on the event         invitee menu data.

The operation of event wizard server 25 in generating and responding to event planning data will be described in greater detail in conjunction with FIGS. 3-14, including several optional functions and features.

FIG. 3 presents a block diagram representation of a client device 100 in accordance with an embodiment of the present invention. In particular, a client device 100, such as mobile terminal 13, personal computer 14 or other client device such as a personal digital assistant, tablet, or smartphone is presented. The client device 100 includes a network interface 120 having one or more interfaces (122, 124 . . . ). Examples of interfaces (122, 124 . . . ) include wireless interfaces such as a 3G, 4G or other wireless telephony transceiver, a Bluetooth transceiver, a WiFi transceiver, UltraWideBand transceiver, WIMAX transceiver, ZigBee transceiver or other wireless interface. Examples of interfaces (122, 124 . . . ) further include wired interfaces such as a Universal Serial Bus (USB) interface, an IEEE 1394 Firewire interface, an Ethernet interface or other network card or modem for communicating with event wizard server 25, or other servers such as content servers 12 via network 15. The client device 100 also includes a user interface such as a display device, touch screen, key pad, touch pad, thumb wheel, one or more buttons, a speaker, a microphone, an accelerometer, gyroscope or other motion sensor, or other interface devices that provide information to a user of the client device 100 and that generate data in response to the user's interaction with the client device 100.

The client device 100 also includes a processing module 130 and memory module 140 that stores an operating system 44 such as a Linux-based operating system, a Microsoft personal computer or mobile operating system, an Android operating system, an Apple mobile or personal computer operating system or other operating system. The memory module 140 also stores location data 42 corresponding to the location of the client device 100 generated via user interaction with user interface 142, via optional Global Positioning System (GPS) receiver 144, or gathered via a wireless network such as triangulation data received from a 4G network, location information from a connected access point or base station, femtocell or other location data. In addition, memory module 140 includes a messaging application 46 for communicating with other client devices such as an email application, a text, instant messaging or short messaging service (SMS) application or other messaging application that stored contacts data corresponding to users of other client devices that are known to the user of client device 100.

The memory module 140 also stores an event wizard client application 150 that is prestored in the memory module, loaded via disk or downloaded to the memory module via network interface 120. The event wizard client application can be a general browser application such as Mozilla, Google Chrome, Safari, Internet Explorer or other general web browser or an application that is customized to operate in conjunction with event wizard server 25 in conjunction with the exchange of event planning data.

The processing module 130 can be implemented via a single processing device or a plurality of processing devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory of memory module 140. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. While a particular bus architecture is presented that includes a single bus 160, other architectures are possible including additional data buses and/or direct connectivity between one or more elements. Further, the client device 100 can include one or more additional elements that are not specifically shown.

The operation of client device in generating and responding to event planning data will be described in greater detail in conjunction with FIGS. 4-14, including several optional functions and features.

FIG. 4 presents a graphical representation of screen display 300 in accordance with an embodiment of the present invention. In particular, a screen display 300 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. The screen display 300 includes event type menu data that includes a plurality of general event types 304 that can be planned based on a plurality of specific events 306. The specific events 306 differ from the general events 304 by being preplanned with more limited choices. An example of a specific event is a mystery dinner at a local dinner theatre for 8-12, where the only choices are the number of people to attend and a seating category (basic or premium). Specific events 306 are presented to cater to user of client device 100 that wish to forego much of the customization of a more complicated event.

In operation, the user selects either a general event type 304 or specific event 306 by clicking, touching or highlighting a particular selection. The user interface 142, in response to the actions of the user to select a general event type or a specific event, generates event type selection data that indicates the selected event type. This event type selection data is sent to the event wizard server 25 via network interface 120.

Display screen 300 includes one or more advertisements such as banner ad 302 or other advertisements. In an embodiment of the present invention, event wizard server 25 includes either a specific advertisement in the event planning data sent to client device 100 or links to a content server 12, such as a remote ad server that supplies ads to the client device 100 for inclusion in the display screen 300. Examples of such remote ad servers include Google ads, Doubleclick ads, etc. When a user selects an advertisement 302, advertising data is retrieved via a universal resource locator (URL), a custom URL or other links via the network 15. In the example shown for “Ruth's Brisket Steakhouse”, when the ad 302 is selected by the user, information pertaining to the menu, location, hours of operation, etc., are retrieved from a remote server and presented for display on the user interface 142 of client device 100.

FIG. 5 presents a graphical representation of screen display 310 in accordance with an embodiment of the present invention. In particular, a screen display 310 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. Display screen 310 presents event option menu data that includes a plurality of event options including the option 314 to create an invitation list, an option 316 to select a budget, an option 318 to select entertainment, an option 320 to select a venue, an option 322 to create online invitations, and an option 324 to select a caterer. It should be noted that while particular options are presented, other options such as a selection of transportation, event supplies, equipment rentals and other event options can be presented in a similar manner.

In the example shown, the each of the options 314, 316, 318, 320, 322, and 324 provide a particular category of event options that are selectable and provide links to other menus that provide additional event options corresponding to the specific category. In an embodiment, the specific event option categories that are presented and/or the event options that are presented within a category are generated by the processing module of the event wizard server 25 based on the event selection data that indicates the type of event selected and optionally based on location data received by the client device 100 that indicates the location of the client device. In this fashion, the event categories can change based on the type of event, with different categories being presented for a Dinner Party as opposed to a Wedding, for example. Further specific choices for event venues, entertainment choices, caterers, etc., can be presented that are local to or otherwise in the vicinity of the user of client device 100 or otherwise in a location selected by the user of client device 100.

Also presented in this example, option 314 includes a first option that is selectable via the user of client device 100 to use local contacts data, such as the contacts data from the messaging application 46 of the client device 100. A second option is presented to allow the wizard or to import contacts from a remote location, such as a social media server, such as Facebook, LinkedIn or Twitter or a web-based messaging service such as Gmail, Yahoo mail, etc. that has an account associated with the user. In this fashion, the user of client device can create an invitation list for the event by starting from an existing list of contacts for the user.

FIG. 6 presents a graphical representation of screen display 330 in accordance with an embodiment of the present invention. In particular, a screen display 330 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. In this example, event planning data is presented for display 328 that queries the user of client device regarding the use of location data. For example if the user responds by selected “yes” as indicated, stored location data 42 corresponding to the location of the client device 100 generated via GPS receiver 144, or gathered via a wireless network such as triangulation data received from a 4G network, location information from a connected access point or base station, femtocell or other stored location data 42 of the client device is used, as previously discussed, to guide the event wizard server 25 in presenting event options that are near the user of client device 100. As further shown, the user of client device 328 is given the option to enter a different location, for example by zip code, zip+4, GPS coordinates, street address or other location in order to guide the event wizard server 25, in situations where the user does not wish to use location data 42, location data 42 is absent or the event will be at a different location than the location reflected by location data 42.

In the example shown, when the user selects that the location can be used, the event wizard client application retrieves the location data 42 and sends the location data 42 to the event wizard server 25 via network interface 120 and network 15. When the user enters different location data, this alternative location data is sent to the event wizard server 25 in a similar fashion.

FIG. 7 presents a graphical representation of screen display 340 in accordance with an embodiment of the present invention. In particular, a screen display 340 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. In the example shown, the menu 332 presents event size selection data received from user interface 142 of client device 100 indicating that there will be 8 attendees. While the example shown presents the size of event by a single number, in other embodiments, ranges of numbers can be employed. The event size selection data can be used by the event wizard server application and/or the event wizard client application in the budgeting process, and otherwise to filter event venues, entertainment options, caterers and other event options that may be particular to events of particular sizes.

In addition, the menu 332 presents event budget menu data that includes a plurality of budget options that are based on the event selection data, the event size selection data and the location data. In the example shown, the menu 332 reflects that a particular event type, “home dinner party” has been selected and presents various budget options (basic, moderate, elegant and over the top) for this event type, with per person (pp) costs particular to the location and the size of the event. In response to menu 332, the user interface 142 generates event budget selection data that indicates a selected one of the plurality of budget options (in this case “elegant”). Event budget data is generated and displayed in response to the selected one of the plurality of budget options that reflects the budget. In this example, with 8 attendees and a $250 pp price, the budget is estimated at $2000.

As the event wizard continues, various event options are presented to the user via the user interface 142 that displays costs associated with additional event options. The event wizard server application and/or the event wizard client application operate to update the event budget data as new options are selected to present the estimated costs of the event. In one example of operation, the event budget data is updated and displayed each time the event options are selected and modified in order to provide a snapshot of the updated cost. In this fashion, the user of client device 100 can plan the event based on the costs of various options—with an eye for the overall budget.

FIG. 8 presents a graphical representation of screen display 350 in accordance with an embodiment of the present invention. In particular, a screen display 350 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. Menu 342 is presented that includes event option menu data pertaining to entertainment options. In this example, for two entertainment options “Awake at the Wheel” and “Twilight Dan” are presented for the selected event, the home dinner party discussed in conjunction with the example of FIG. 7. As previously discussed, the particular options presented can be generated by the event wizard server application based on the location data, and the event selection data. In this example, entertainment options that may be appropriate to a home dinner party and that are in the vicinity indicated by the location data are selected by the event wizard server application 250 to be presented to the user.

The user interface 142 responds to actions of the user of client device 100 to generate event option selection data that indicates the user's selection of particular event option menu data. In the example shown, the total estimated budget for the event of $2000 is shown as well as the particular budget for this portion of the event, $400 for the entertainment. The two options shown in this example each have an associated cost that is displayed. In this case, the user can see that one choice matches the budget while the other choice, if selected, would save $150. Graphics are presented for each option and links are provided to additional information such as songs by one group and example playlists of the other. When a selection is made, the budget data in the form of the total estimated budget is updated to reflect any change in cost.

FIG. 9 presents a graphical representation of screen display 360 in accordance with an embodiment of the present invention. In particular, a screen display 300 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. Menu 352 is presented that includes event invitee menu data generated by the event wizard server application 250 and/or the event wizard client application 150 that includes contacts data corresponding to the user that is retrieved from either messaging application or (as shown) an external location. In particular, the menu 352 reflects that the contacts presented are imported from a social media server, in this case Facebook. In an embodiment, subscription information for the social media server is obtained from the client device 100 and used to access the data for presentation to the user via user interface 142. The contacts data includes names and images of each contact as shown, but optionally includes mailing addresses, email addresses or other messaging addresses along with other contacts data.

The user interface 142 responds to actions of the user of client device 100 to generate event invitee selection data that indicates the user's selection of particular attendees to the event. In the example shown, the total estimated budget for the event of $2000 is shown as well as the expected number of attendees. As selections of attendees are made, the event budget data (in the form of the total estimated budget) is updated to reflect any change in cost; for example when a greater or fewer number of attendees are selected.

In an embodiment of the present invention, an estimated attendee percentage is applied for selected events. In this fashion, the budget for a large event such as a wedding with 250 invitees is estimated with an estimated attendance percentage of 80% to reflect that some persons that are invited may not attend. The estimated attendance percentage may be selected by the user or selected by the event wizard server application 250 based on the size of the event, the type of event and optionally location data that provides estimated attendance by locale.

In a further embodiment, an invitation server such as Evite is used by the event wizard server 25 to not only to prepare and send the invitations but to track invitee attendance data. In this embodiment, the event wizard server 25 sends the invitee selection data to the invitation server via the network interface 220. As invitee attendance data is received by the invitation server, it is forwarded to the event wizard server and used to update a status menu as to the expected number of attendees. In addition, the event budget data is updated based on the invitee acceptance data received from the invitation server.

FIG. 10 presents a graphical representation of screen display 370 in accordance with an embodiment of the present invention. In particular, a screen display 370 of user interface 142 of client device 100 is presented as generated by the event wizard client application 150 in response to event planning data from the event wizard server application 250. In particular a status menu 362 is presented that indicates the user's selections of various event options, invitees, the event type, etc. Before the event is finalized the user is given the option to edit the selections. As indicated in conjunction with FIG. 7 the event wizard server application 250 and/or the event wizard client application 150 operate to update the event budget data as event options and other selections are modified to present the updated estimated costs of the event in order to provide a snapshot of the updated cost.

In an embodiment, an invitation server such as Evite is used by the event wizard server 25 to not only to prepare and send the invitations but to track invitee attendance data. In this embodiment, the event wizard server 25 sends the invitee selection data to the invitation server via the network interface 220. As invitee attendance data is received by the invitation server, it is forwarded to the event wizard server 25 and used to update status menu 362 as to the expected number of attendees. In addition, the event budget data is updated based on the invitee acceptance data received from the invitation server.

FIG. 11 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular, a method is presented for use in conjunction with one or more functions and features described in FIGS. 1-10. In step 400, event type menu data is generated via a processing module and the event type menu data is sent to a client device, wherein the event type menu data includes a plurality of general event types and a plurality of specific events. In step 402, event type selection data is received from the client device that indicates an event type based on the event type menu data. In step 404, event size selection data is received from the client device that indicates an event size. In step 406, location data is received from the client device. In step 408, event budget menu data is generated via the processing module and the event budget menu data is sent to the client device, wherein the event budget data includes a plurality of budget options that are based on the event selection data, the event size selection data and the location data. In step 408, event budget selection data is received from the client device that indicates a selected one of the plurality of budget options. In step 410, event budget data is generated via the processing module in response to the selected one of the plurality of plurality of budget options, and the event budget data is sent to the client device. In step 412, event option menu data that includes a plurality of event options is generated via the processing module wherein the event option menu data are generated based on the based on the event selection data and the location data, wherein the event options correspond to at least one of: an event venue, an event caterer, an event invitation, event entertainment and event transportation. In step 414, the event option menu data are sent to the client device.

In an embodiment, the event option menu displays costs associated with the plurality of event options. The event size selection data can indicate an estimated number of attendees to the event.

FIG. 12 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular, a method is presented for use in conjunction with one or more functions and features described in FIGS. 1-11. In step 420, event option selection data are received from the client device that indicates selection of at least one event option based on the event option menu data. In step 422, event invitee menu data are generated via the processing module and the event invitee menu data are sent to the client device, wherein the event invitee menu data includes contact data corresponding to the user that is retrieved by the event wizard server from an external location. In step 424, event invitee selection data are received from the client device that indicates a plurality of invitees based on the event invitee menu data. In step 426, the event budget data are updated based on the event option selection data, and the event invitee selection data.

In embodiments, the external location includes a social media server having an account associated with the user or the external location includes a messaging application of the client device. The event invitee menu can display the updated event budget data. The updated event budget data can further be based on an estimated attendance percentage. The processing module can send the invitee selection data to an invitation server via the network interface and the updated event budget data can further be based on invitee acceptance data received from the invitation server.

FIG. 13 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular, a method is presented for use in conjunction with one or more functions and features described in FIGS. 1-12. In step 430, event type menu data is displayed via a user interface of the client device, wherein the event type menu data includes a plurality of general event types and a plurality of specific events. In step 432, event type selection data is received via the user interface that indicates an event type based on the event type menu data. In step 434, event size selection data is received via the user interface that indicates an event size. In step 436, event budget menu data is displayed via the user interface, wherein the event budget menu data includes a plurality of budget options that are based on the event selection data, the event size selection data and location data. In step 438 event budget selection data is received via the user interface that indicates a selected one of the plurality of budget options. In step 440, event budget data are displayed in response to the selected one of the plurality of plurality of budget options. In step 442, event option menu data are displayed via the user interface that includes a plurality of event options, wherein the event option menu data are generated based on the based on the event selection data and location data, wherein the event options correspond to at least one of: an event venue, an event caterer, an event invitation, event entertainment and event transportation.

In an embodiment, the event option menu displays costs associated with the plurality of event options. The event size selection data can indicate an estimated number of attendees to the event.

FIG. 14 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular, a method is presented for use in conjunction with one or more functions and features described in FIGS. 1-13. In step 450, event option selection data are received via the user interface that indicates selection of at least one event option based on the event option menu data. In step 452, event invitee menu data are displayed via the user interface, wherein the event invitee menu data includes contact data corresponding to the user. In step 454 event invitee selection data are received via the user interface that indicates a plurality of invitees based on the event invitee menu data. In step 456, the event budget data are updated based on the event option selection data, and the event invitee selection data.

In embodiments, the external location includes a social media server having an account associated with the user or a messaging application of the client device. The event invitee menu can display the updated event budget data. The updated event budget data can further be based on an estimated attendance percentage. The processing module can send the invitee selection data to an invitation server via the network interface. The updated event budget data can further be based on invitee acceptance data received from the invitation server.

It should be noted that while the foregoing description focuses on a client/server mode of operation between client device 100 and event wizard server 25, some or all of the functionality of the event wizard server application 250 can be combined with the operation of event wizard client application 150 to present the functionality of the system in a single device such as mobile terminal 13 or personal computer 14. In this fashion, the mobile terminal 13 or personal computer 14 operates to generate the event planning data for display, retrieve information from content servers, etc.

As may be used herein, the terms “substantially” and “approximately” provide an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “operable to” or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1.

As may also be used herein, the terms “processing module”, “processing circuit”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.

Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

The present invention has been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

The present invention may have also been described, at least in part, in terms of one or more embodiments. An embodiment of the present invention is used herein to illustrate the present invention, an aspect thereof, a feature thereof, a concept thereof, and/or an example thereof. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process that embodies the present invention may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

While the transistors in the above described figure(s) is/are shown as field effect transistors (FETs), as one of ordinary skill in the art will appreciate, the transistors may be implemented using any type of transistor structure including, but not limited to, bipolar, metal oxide semiconductor field effect transistors (MOSFET), N-well transistors, P-well transistors, enhancement mode, depletion mode, and zero voltage threshold (VT) transistors.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of the various embodiments of the present invention. A module includes a processing module, a functional block, hardware, and/or software stored on memory for performing one or more functions as may be described herein. Note that, if the module is implemented via hardware, the hardware may operate independently and/or in conjunction software and/or firmware. As used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

While particular combinations of various functions and features of the present invention have been expressly described herein, other combinations of these features and functions are likewise possible. The present invention is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A client device comprising: a user interface; a network interface for communicating via a network; a memory that stores an event wizard client application and location data; a processing module, coupled to the memory, the user interface and the network interface, the processing module including at least one processor that executes the event wizard client application by: displaying event type menu data via the user interface that includes a plurality of general event types and a plurality of specific events; receiving event type selection data via the user interface that indicates an event type based on the event type menu data; receiving event size selection data via the user interface that indicates an event size; displaying event budget menu data generated via the user interface that includes a plurality of budget options that are based on the event selection data, the event size selection data and the location data; receiving event budget selection data via the user interface that indicates a selected one of the plurality of budget options; displaying event budget data in response to the selected one of the plurality of plurality of budget options; displaying event option menu data via the user interface that includes a plurality of event options that are generated based on the event selection data and the location data, wherein the event options correspond to at least one of: an event venue, an event caterer, an event invitation, event entertainment and event transportation; receiving event option selection data via the user interface that selects at least one event option based on the event option menu data; displaying event invitee menu data via the user interface that includes contact data corresponding to the user; and receiving event invitee selection data via the user interface that indicates a plurality of invitees based on the event invitee menu data.
 2. The client device of claim 1 wherein the event option menu displays costs associated with the plurality of event options and the event budget data is updated based on the event option selection data.
 3. The event wizard server of claim 1 wherein the content data are retrieved from a social media server having an account associated with the user via the network interface.
 4. The event wizard server of claim 1 wherein the content data are retrieved from a messaging application stored in the memory.
 5. The event wizard server of claim 1 wherein the event size selection data indicates an estimated number of attendees to the event.
 6. The event wizard server of claim 1 wherein the event budget data is updated to generate updated event budget data based on the event invitee selection data.
 7. The event wizard server of claim 6 wherein the event invitee menu includes the updated event budget data.
 8. The event wizard server of claim 1 wherein the event budget data is updated based on the event invitee selection data and an estimated attendance percentage.
 9. The event wizard server of claim 1 wherein the processing module sends the invitee selection data to an invitation server via the network interface.
 10. The event wizard server of claim 9 wherein the event budget data is updated based on the event invitee selection data and invitee acceptance data received from the invitation server.
 11. A method for use in a client device, the method comprising: displaying event type menu data via a user interface of the client device, wherein the event type menu data includes a plurality of general event types and a plurality of specific events; receiving event type selection data via the user interface that indicates an event type based on the event type menu data; receiving event size selection data via the user interface that indicates an event size; displaying event budget menu data via the user interface, wherein the event budget menu data includes a plurality of budget options that are based on the event selection data, the event size selection data and location data; receiving event budget selection data via the user interface that indicates a selected one of the plurality of budget options; displaying event budget data in response to the selected one of the plurality of plurality of budget options; displaying event option menu data via the user interface that includes a plurality of event options, wherein the event option menu data are generated based on the based on the event selection data and location data, wherein the event options correspond to at least one of: an event venue, an event caterer, an event invitation, event entertainment and event transportation; receiving event option selection data via the user interface that indicates selection of at least one event option based on the event option menu data; displaying event invitee menu data via the user interface, wherein the event invitee menu data includes contact data corresponding to the user; receiving event invitee selection data via the user interface that indicates a plurality of invitees based on the event invitee menu data; and updating the event budget data based on the event option selection data, and the event invitee selection data.
 12. The method of claim 11 wherein the event option menu displays costs associated with the plurality of event options.
 13. The method of claim 11 wherein the external location includes a social media server having an account associated with the user.
 14. The method of claim 11 wherein the external location includes a messaging application of the client device.
 15. The method of claim 11 wherein the event size selection data indicates an estimated number of attendees to the event.
 16. The method of claim 11 wherein the event invitee menu displays the updated event budget data.
 17. The method of claim 11 wherein the updated event budget data is further based on an estimated attendance percentage.
 18. The method of claim 11 wherein the processing module sends the invitee selection data to an invitation server via the network interface.
 19. The method of claim 18 wherein the updated event budget data is further based on invitee acceptance data received from the invitation server.
 20. A client device comprising: a user interface; a network interface for communicating via a network; a memory that stores an event wizard client application and location data; a processing module, coupled to the memory, the user interface and the network interface, the processing module including at least one processor that executes the event wizard client application by: displaying event type menu data via the user interface that includes a plurality of general event types and a plurality of specific events; receiving event type selection data via the user interface that indicates an event type based on the event type menu data; receiving event size selection data via the user interface that indicates an event size; displaying event budget menu data generated via the user interface that includes a plurality of budget options that are based on the event selection data, the event size selection data and the location data; receiving event budget selection data via the user interface that indicates a selected one of the plurality of budget options; displaying event budget data in response to the selected one of the plurality of plurality of budget options; displaying event option menu data via the user interface that includes a plurality of event options that are generated based on the event selection data and the location data, wherein the event options correspond to at least one of: an event venue, an event caterer, an event invitation, event entertainment and event transportation; receiving event option selection data via the user interface that selects at least one event option based on the event option menu data; displaying event invitee menu data via the user interface that includes contact data corresponding to the user; and receiving event invitee selection data via the user interface that indicates a plurality of invitees based on the event invitee menu data. wherein the event option menu displays costs associated with the plurality of event options and the event budget data is updated based on the event option selection data and the event invitee selection data. 